Re: [GENERAL] GEQO and KSQO problem.
От | Herouth Maoz |
---|---|
Тема | Re: [GENERAL] GEQO and KSQO problem. |
Дата | |
Msg-id | l03130301b3f95ce73682@[147.233.159.109] обсуждение исходный текст |
Ответ на | GEQO and KSQO problem. ("Natalya S. Makushina" <mak@rtsoft.msk.ru>) |
Список | pgsql-general |
At 11:45 +0300 on 02/09/1999, Natalya S. Makushina wrote: > where CLIENTS.CLIENTID=SOTRUD.CLIENTID and > ( CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and (NOT >CLIENTS.ARH) and lower(SOTRUD.EMAIL) LIKE lower('%ruslanmr@hotmail.com%') > OR CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and (not >CLIENTS.ARH) and lower(SOTRUD.EMAIL) LIKE lower('%matukin@hotmail.com%') > OR CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and (not >CLIENTS.ARH) and lower(SOTRUD.EMAIL) LIKE lower('%knirti@kaluga.ru%') > OR CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and (not >CLIENTS.ARH) and lower(SOTRUD.EMAIL) LIKE lower('%avk@vniicom.vsu.ru%') > OR CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and (not >CLIENTS.ARH) and lower(SOTRUD.EMAIL) LIKE lower('%avk@vniicom.vsu.ru%') > ) > order by CLIENTS.NEW_F, CLIENTS.NAME_1" I wonder if this is all necessary? Can't you take the part CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and (not CLIENTS.ARH) Outside the parentheses and leave only the LIKE comparisons inside? Also, there is no point in running "lower" on a string which is known in advance to contain only lowercase letters, which is true for most literal strings (If your application creates this, you can always do the conversion on the client side before putting it into the query). It only leaks memory. Thus, if you try to rewrite the WHERE clause as follows, do you get any improvement? where CLIENTS.CLIENTID=SOTRUD.CLIENTID and CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and not CLIENTS.ARH and ( lower(SOTRUD.EMAIL) LIKE '%ruslanmr@hotmail.com%' or lower(SOTRUD.EMAIL) LIKE '%matukin@hotmail.com%' or lower(SOTRUD.EMAIL) LIKE '%knirti@kaluga.ru%' or lower(SOTRUD.EMAIL) LIKE '%avk@vniicom.vsu.ru%' ) ... I think the optimizer would be most happy if you avoid the OR altogether by using alternatives in a regular expression instead of like. This will also allow you to use case insensitive comparison and give up the 'lower': where CLIENTS.CLIENTID=SOTRUD.CLIENTID and CLIENTS.PRINADL=PRINADLEG.PRINADL and CLIENTS.FLG_MY and not CLIENTS.ARH and SORTUD.EMAIL ~* 'ruslanmr@hotmail\\.com|matukin@hotmail\\.com|knirti@kaluga\\.ru|avk@vniicom\\.v su\\.ru'; Note that you have to put two slashes before each period in the string, because a period is special in regular expressions. Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma ************
В списке pgsql-general по дате отправления: